Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74d3c1e6cd043aeb546189891c6da42495dae156eb3d9c3910043157baf853f1

Tx prefix hash: 61dc3789e6d61dd86c88a41c4d91b43fb41c1beae66e3c61b2957ac9ae42c737
Tx public key: 49535ec8add9c822bf7d2716abacff51996240cf004fc65d273c00db0156c53b
Timestamp: 1685572984 Timestamp [UCT]: 2023-05-31 22:43:04 Age [y:d:h:m:s]: 02:001:12:52:43
Block: 772390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523209 RingCT/type: yes/0
Extra: 0149535ec8add9c822bf7d2716abacff51996240cf004fc65d273c00db0156c53b0211000000014b8f5122000000000000000000

1 output(s) for total of 1.693368458000 dcy

stealth address amount amount idx
00: a815a1b34c5cdd1a2b9e5a342086fe7b7ed4ca0df4f085c4dbfb9140787011fa 1.693368458000 1221791 of 0

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": 772400, "vin": [ { "gen": { "height": 772390 } } ], "vout": [ { "amount": 1693368458, "target": { "key": "a815a1b34c5cdd1a2b9e5a342086fe7b7ed4ca0df4f085c4dbfb9140787011fa" } } ], "extra": [ 1, 73, 83, 94, 200, 173, 217, 200, 34, 191, 125, 39, 22, 171, 172, 255, 81, 153, 98, 64, 207, 0, 79, 198, 93, 39, 60, 0, 219, 1, 86, 197, 59, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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