Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dc8366abc2d0d7559a8f6f379f6ab7aa8fb99fcc634c59ec939985aa01b495f

Tx prefix hash: 9a8a5c934148feffe6b89f6290deaedc03b2c60668cfa4820b2b4a8ecee7ae8e
Tx public key: 3574e008775a2d8c57c016e8c57e8c9e83b76a9a0987d0d877af8c23afdc33b4
Timestamp: 1724110616 Timestamp [UCT]: 2024-08-19 23:36:56 Age [y:d:h:m:s]: 00:231:00:28:30
Block: 1091640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164961 RingCT/type: yes/0
Extra: 013574e008775a2d8c57c016e8c57e8c9e83b76a9a0987d0d877af8c23afdc33b402110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfde09fc3ffaed0d981e4e496103f830aef76e967446180d5e9782e84ed44d21 0.600000000000 1566273 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": 1091650, "vin": [ { "gen": { "height": 1091640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfde09fc3ffaed0d981e4e496103f830aef76e967446180d5e9782e84ed44d21" } } ], "extra": [ 1, 53, 116, 224, 8, 119, 90, 45, 140, 87, 192, 22, 232, 197, 126, 140, 158, 131, 183, 106, 154, 9, 135, 208, 216, 119, 175, 140, 35, 175, 220, 51, 180, 2, 17, 0, 0, 0, 7, 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