Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b47e43a6fa4b16d25c2f186b5d44ebb8bc9e587bad4e807254b5edeaf2f8424

Tx prefix hash: 9a7b987b56afcea18eeadd8c8ab94e78fa5ee0048499845cf3cec32dcc4d6533
Tx public key: d61e8a6f86d0776fc3e8e98ff918880dc66d4fb913aa2b4aad8c4385e6e843c9
Timestamp: 1721026983 Timestamp [UCT]: 2024-07-15 07:03:03 Age [y:d:h:m:s]: 00:253:21:50:33
Block: 1066081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181357 RingCT/type: yes/0
Extra: 01d61e8a6f86d0776fc3e8e98ff918880dc66d4fb913aa2b4aad8c4385e6e843c9021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 282d3c9478944ff46bb668283506edb613c34f44b6b3c9c49e0245cc6507f95d 0.600000000000 1536652 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": 1066091, "vin": [ { "gen": { "height": 1066081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "282d3c9478944ff46bb668283506edb613c34f44b6b3c9c49e0245cc6507f95d" } } ], "extra": [ 1, 214, 30, 138, 111, 134, 208, 119, 111, 195, 232, 233, 143, 249, 24, 136, 13, 198, 109, 79, 185, 19, 170, 43, 74, 173, 140, 67, 133, 230, 232, 67, 201, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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