Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf4022d4dec8b8c556e5f1f2f4b18e146d13ac936ae22e19b1945ae0f045c8ae

Tx prefix hash: 9c947e0c72eb675dcb95068b7592d0721ce5d2bc8eb190bd161665ae4dde9178
Tx public key: 8073dd9a45f131015ae960457a9d2d0bea94d784175a9d49f9ec9af3f7152054
Timestamp: 1725472032 Timestamp [UCT]: 2024-09-04 17:47:12 Age [y:d:h:m:s]: 00:224:10:28:10
Block: 1102924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160244 RingCT/type: yes/0
Extra: 018073dd9a45f131015ae960457a9d2d0bea94d784175a9d49f9ec9af3f715205402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb4283315ff80b48e9109a66be18a65680e30328a13f4e1671714f0a73edfb99 0.600000000000 1579549 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": 1102934, "vin": [ { "gen": { "height": 1102924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb4283315ff80b48e9109a66be18a65680e30328a13f4e1671714f0a73edfb99" } } ], "extra": [ 1, 128, 115, 221, 154, 69, 241, 49, 1, 90, 233, 96, 69, 122, 157, 45, 11, 234, 148, 215, 132, 23, 90, 157, 73, 249, 236, 154, 243, 247, 21, 32, 84, 2, 17, 0, 0, 0, 3, 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