Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30b328591fd6196ee5d56dd1a791c02075258642c914525059fe22b45cd1ea11

Tx prefix hash: 40635a80ce3fca056289cf1462385c8c5a74ec9e77ebb3350bba688048d7a54d
Tx public key: 441d294a8f2b247d2fdf2a306247799dbaf75da9e29ad5875dc78efc3f3cd2eb
Timestamp: 1663004495 Timestamp [UCT]: 2022-09-12 17:41:35 Age [y:d:h:m:s]: 03:053:12:08:41
Block: 586478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 818106 RingCT/type: yes/0
Extra: 01441d294a8f2b247d2fdf2a306247799dbaf75da9e29ad5875dc78efc3f3cd2eb0211000000016035bcb5000000000000000000

1 output(s) for total of 6.994473132000 dcy

stealth address amount amount idx
00: f1832d1896a0665adc4262c76931a84760a408f5c8a5b6ecd40bd9fa0e4579f2 6.994473132000 1020587 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": 586488, "vin": [ { "gen": { "height": 586478 } } ], "vout": [ { "amount": 6994473132, "target": { "key": "f1832d1896a0665adc4262c76931a84760a408f5c8a5b6ecd40bd9fa0e4579f2" } } ], "extra": [ 1, 68, 29, 41, 74, 143, 43, 36, 125, 47, 223, 42, 48, 98, 71, 121, 157, 186, 247, 93, 169, 226, 154, 213, 135, 93, 199, 142, 252, 63, 60, 210, 235, 2, 17, 0, 0, 0, 1, 96, 53, 188, 181, 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