Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f40052226bb22ee84caa648fd4b6c4dc2e6db3af1c507f2414cb5cae083acf2

Tx prefix hash: f1207dc4902beeb481aeddd9b37a454560c9c556cde27d91e2211d58b0edc5f9
Tx public key: ed37cb365fbd6e46ce334ac74e7b0bfa7dbd19f70d0af175962dbdb7111ee2d5
Timestamp: 1740728046 Timestamp [UCT]: 2025-02-28 07:34:06 Age [y:d:h:m:s]: 00:266:10:10:33
Block: 1228935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188165 RingCT/type: yes/0
Extra: 01ed37cb365fbd6e46ce334ac74e7b0bfa7dbd19f70d0af175962dbdb7111ee2d5021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d854774c5c3dccfd15662a3d28874663b61d29a6a3d760c88aa13e47cf98c98 0.600000000000 1715816 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": 1228945, "vin": [ { "gen": { "height": 1228935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d854774c5c3dccfd15662a3d28874663b61d29a6a3d760c88aa13e47cf98c98" } } ], "extra": [ 1, 237, 55, 203, 54, 95, 189, 110, 70, 206, 51, 74, 199, 78, 123, 11, 250, 125, 189, 25, 247, 13, 10, 241, 117, 150, 45, 189, 183, 17, 30, 226, 213, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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