Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0b920670994c7c8fcb34df78fdfce90908a96b06310ccd18096f39ab2d4060b

Tx prefix hash: 348319a3f164423e7fb1b2f16c6cb71ef7a593b7a6f647b723a7e632896de2a4
Tx public key: 207c2a709261816d1d80f97b91a42180d100d70721cdade04d6a8a766d70d8ea
Timestamp: 1729058559 Timestamp [UCT]: 2024-10-16 06:02:39 Age [y:d:h:m:s]: 00:039:08:06:17
Block: 1132664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28074 RingCT/type: yes/0
Extra: 01207c2a709261816d1d80f97b91a42180d100d70721cdade04d6a8a766d70d8ea02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c23626b7611a0b56652e48a81bf53576693753fec475370e934df2447cd6701 0.600000000000 1615633 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": 1132674, "vin": [ { "gen": { "height": 1132664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c23626b7611a0b56652e48a81bf53576693753fec475370e934df2447cd6701" } } ], "extra": [ 1, 32, 124, 42, 112, 146, 97, 129, 109, 29, 128, 249, 123, 145, 164, 33, 128, 209, 0, 215, 7, 33, 205, 173, 224, 77, 106, 138, 118, 109, 112, 216, 234, 2, 17, 0, 0, 0, 1, 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