Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d8b9db5174f6be53025c3cebd67ec29c461080ece9a7ea8c6284181ffc58165

Tx prefix hash: 766013cf79fcfaf01005d2d7ec90a0fec8d9444c62a8f3c53355a03add58a0a7
Tx public key: 9e49a29b4fc896ebe1add248c861725f8d8ef85e27c1151ddf43fd2c9fd0d1be
Timestamp: 1759218506 Timestamp [UCT]: 2025-09-30 07:48:26 Age [y:d:h:m:s]: 00:007:21:31:55
Block: 1379572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5648 RingCT/type: yes/0
Extra: 019e49a29b4fc896ebe1add248c861725f8d8ef85e27c1151ddf43fd2c9fd0d1be02110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3588065a1fc1568065dcdab07fc40f462f17e0548b81c0da839de85c8fb6d50 0.600000000000 1867671 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": 1379582, "vin": [ { "gen": { "height": 1379572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3588065a1fc1568065dcdab07fc40f462f17e0548b81c0da839de85c8fb6d50" } } ], "extra": [ 1, 158, 73, 162, 155, 79, 200, 150, 235, 225, 173, 210, 72, 200, 97, 114, 95, 141, 142, 248, 94, 39, 193, 21, 29, 223, 67, 253, 44, 159, 208, 209, 190, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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