Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fec2bcd796cb6283617fdd90a67dd4649992495ea904f42dfc44e7c9fefd264

Tx prefix hash: 6e65e81d20cc4ef499edc04d78fa9323d6df8df4963913aedf4cb36a086a315f
Tx public key: a50ff1c799579ca6d0f5260df6ff8ccf79d3e3272aa51a85d152450d9b361249
Timestamp: 1714301316 Timestamp [UCT]: 2024-04-28 10:48:36 Age [y:d:h:m:s]: 01:205:11:56:25
Block: 1010309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405519 RingCT/type: yes/0
Extra: 01a50ff1c799579ca6d0f5260df6ff8ccf79d3e3272aa51a85d152450d9b3612490211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 368e02012c32a5e0fe0e09817bb2a32dad37ff07ac6599dcbba3f27c057832a6 0.600000000000 1472223 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": 1010319, "vin": [ { "gen": { "height": 1010309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "368e02012c32a5e0fe0e09817bb2a32dad37ff07ac6599dcbba3f27c057832a6" } } ], "extra": [ 1, 165, 15, 241, 199, 153, 87, 156, 166, 208, 245, 38, 13, 246, 255, 140, 207, 121, 211, 227, 39, 42, 165, 26, 133, 209, 82, 69, 13, 155, 54, 18, 73, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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