Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4c78c81a26e1c1dc5f70283bb73aa40d258d369ebb94bfe66ebcb698193052e4

Tx prefix hash: 341b00fbd1f16212339f91fa812d3d730b0a1634ad73ab842472c533f03ba38c
Tx public key: 11c1e5d8fb1f6930ccf51b91b1d4385d9c607553061364cfd44622a3f07a04e7
Timestamp: 1721531387 Timestamp [UCT]: 2024-07-21 03:09:47 Age [y:d:h:m:s]: 00:243:14:22:11
Block: 1070248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174018 RingCT/type: yes/0
Extra: 0111c1e5d8fb1f6930ccf51b91b1d4385d9c607553061364cfd44622a3f07a04e702110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 935c65dfa9c63575edea4ed4d71b23fea8343aac5156c3f76f0b0f179636196a 0.600000000000 1542001 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1070258, "vin": [ { "gen": { "height": 1070248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "935c65dfa9c63575edea4ed4d71b23fea8343aac5156c3f76f0b0f179636196a" } } ], "extra": [ 1, 17, 193, 229, 216, 251, 31, 105, 48, 204, 245, 27, 145, 177, 212, 56, 93, 156, 96, 117, 83, 6, 19, 100, 207, 212, 70, 34, 163, 240, 122, 4, 231, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8