Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 462c5d13957dae410456a594ab308cad1761b1ea32277dad1847d9fe1c5c7ba5

Tx prefix hash: 7508e878422379e642a1453847713aae292fb0dcc0122a541ffc99b400c5e5ba
Tx public key: c25b22ac7936c4b8c0e06c880f333cd13bf634b2701c8ec10c766e2cf4ca9878
Timestamp: 1721193725 Timestamp [UCT]: 2024-07-17 05:22:05 Age [y:d:h:m:s]: 01:113:23:53:21
Block: 1067471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339966 RingCT/type: yes/0
Extra: 01c25b22ac7936c4b8c0e06c880f333cd13bf634b2701c8ec10c766e2cf4ca987802110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d704a04b99a39f63a6beae28f6c058b4a818bfb228ca2b6c873db9ece2602fb 0.600000000000 1538288 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": 1067481, "vin": [ { "gen": { "height": 1067471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d704a04b99a39f63a6beae28f6c058b4a818bfb228ca2b6c873db9ece2602fb" } } ], "extra": [ 1, 194, 91, 34, 172, 121, 54, 196, 184, 192, 224, 108, 136, 15, 51, 60, 209, 59, 246, 52, 178, 112, 28, 142, 193, 12, 118, 110, 44, 244, 202, 152, 120, 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