Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d88a3d581ee98a1eddf861bdaa4f985b0de8ec21c2f65d706d69275923cc24ac

Tx prefix hash: 904ca3f64d275f976ec6d618f60de86720f739fba442826187bf79075cdd6614
Tx public key: 397786bc5593ba468fcd6529c764f0312e40d0ecd5f12a0b8dbe913f3dd4ac63
Timestamp: 1726257949 Timestamp [UCT]: 2024-09-13 20:05:49 Age [y:d:h:m:s]: 00:130:22:11:54
Block: 1109434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93593 RingCT/type: yes/0
Extra: 01397786bc5593ba468fcd6529c764f0312e40d0ecd5f12a0b8dbe913f3dd4ac63021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d932d7928d2751ae6a3d09e09144988e7cdf231cc26631a4fb2a60b32fee7a56 0.600000000000 1587689 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": 1109444, "vin": [ { "gen": { "height": 1109434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d932d7928d2751ae6a3d09e09144988e7cdf231cc26631a4fb2a60b32fee7a56" } } ], "extra": [ 1, 57, 119, 134, 188, 85, 147, 186, 70, 143, 205, 101, 41, 199, 100, 240, 49, 46, 64, 208, 236, 213, 241, 42, 11, 141, 190, 145, 63, 61, 212, 172, 99, 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