Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c31b706e3117ce788151a479b61f7256764ef3b9ec7181b06e9fc53a6b3e959

Tx prefix hash: f05352f39bd8946a7cd80cb7814f16ee674fd45982f9899dfbd422eccc4a792d
Tx public key: 27da0f70c3bf0ce796fa8ae286b18d0c6235675e68cbaf10f23b1d3073a6daef
Timestamp: 1726969907 Timestamp [UCT]: 2024-09-22 01:51:47 Age [y:d:h:m:s]: 00:109:07:16:16
Block: 1115339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78158 RingCT/type: yes/0
Extra: 0127da0f70c3bf0ce796fa8ae286b18d0c6235675e68cbaf10f23b1d3073a6daef02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bda4258a5217f8a69a8ee835e55828bc9b3000953775a4649a5df330d252b76 0.600000000000 1595438 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": 1115349, "vin": [ { "gen": { "height": 1115339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bda4258a5217f8a69a8ee835e55828bc9b3000953775a4649a5df330d252b76" } } ], "extra": [ 1, 39, 218, 15, 112, 195, 191, 12, 231, 150, 250, 138, 226, 134, 177, 141, 12, 98, 53, 103, 94, 104, 203, 175, 16, 242, 59, 29, 48, 115, 166, 218, 239, 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