Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b6030bcda80178d65237b31f5460e710c067aca9ef0cd80da07225303028f8e

Tx prefix hash: 7d69af29f60aff4ea95dc435e8ee857e31a74265720ee85d88f8b72e2528d584
Tx public key: d53d5736ae0d25bbf4ce96497e21021694cb3a1f6abcae0559e91fe01cb3c5e9
Timestamp: 1712659647 Timestamp [UCT]: 2024-04-09 10:47:27 Age [y:d:h:m:s]: 01:018:08:14:00
Block: 996682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274093 RingCT/type: yes/0
Extra: 01d53d5736ae0d25bbf4ce96497e21021694cb3a1f6abcae0559e91fe01cb3c5e90211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21d778dc7065a4d8510e4c1c278d4fa7e515ad0d36d39fcc44091cf106095a06 0.600000000000 1457108 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": 996692, "vin": [ { "gen": { "height": 996682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21d778dc7065a4d8510e4c1c278d4fa7e515ad0d36d39fcc44091cf106095a06" } } ], "extra": [ 1, 213, 61, 87, 54, 174, 13, 37, 187, 244, 206, 150, 73, 126, 33, 2, 22, 148, 203, 58, 31, 106, 188, 174, 5, 89, 233, 31, 224, 28, 179, 197, 233, 2, 17, 0, 0, 0, 1, 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