Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc808f08261abc876605361cd5a099b4018083f4d55b5de0935a424493435aab

Tx prefix hash: 9e4c6acbeb52044b17581421a68648336d2f497d9a5af3800c94d1d027c9feaf
Tx public key: debad8ad78b70e4d687910c2fc531dd1c0f01b4acdfe2f2695467584d8e8ad0c
Timestamp: 1718862432 Timestamp [UCT]: 2024-06-20 05:47:12 Age [y:d:h:m:s]: 00:286:03:19:53
Block: 1048126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204458 RingCT/type: yes/0
Extra: 01debad8ad78b70e4d687910c2fc531dd1c0f01b4acdfe2f2695467584d8e8ad0c0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e87c12a435081d8549fec5615c322c3b8bbd11696eea7b201ec107aa9ee96cce 0.600000000000 1518129 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": 1048136, "vin": [ { "gen": { "height": 1048126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e87c12a435081d8549fec5615c322c3b8bbd11696eea7b201ec107aa9ee96cce" } } ], "extra": [ 1, 222, 186, 216, 173, 120, 183, 14, 77, 104, 121, 16, 194, 252, 83, 29, 209, 192, 240, 27, 74, 205, 254, 47, 38, 149, 70, 117, 132, 216, 232, 173, 12, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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