Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b194b45d4df1c121e6ee75c5e2b71de7dd308f29cb9ebe185482655b2da1c949

Tx prefix hash: 430475ada0e4e9e8603ebd6f08452f6a0c145381458cae39652085a60a4cbec1
Tx public key: 2ba5ad40093ed9e6eb90d01f54517f6b85de53e549ffcbf5a0b86e5f66cfbdbe
Timestamp: 1738053209 Timestamp [UCT]: 2025-01-28 08:33:29 Age [y:d:h:m:s]: 00:043:18:30:58
Block: 1206820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31305 RingCT/type: yes/0
Extra: 012ba5ad40093ed9e6eb90d01f54517f6b85de53e549ffcbf5a0b86e5f66cfbdbe021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af7413d6aa6872a876d5c29eb2357e21702e0079e2b84a7bb6ef5870683e3555 0.600000000000 1693533 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": 1206830, "vin": [ { "gen": { "height": 1206820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af7413d6aa6872a876d5c29eb2357e21702e0079e2b84a7bb6ef5870683e3555" } } ], "extra": [ 1, 43, 165, 173, 64, 9, 62, 217, 230, 235, 144, 208, 31, 84, 81, 127, 107, 133, 222, 83, 229, 73, 255, 203, 245, 160, 184, 110, 95, 102, 207, 189, 190, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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