Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46d90bbd764c94ce638ab0e9c55ae48859e66489c26f5981e6cd68aaf3e49f89

Tx prefix hash: 0db412227e98ef08eeb4f2c3c85c33355ca542bddea8aa7c9f000eadf7dfcadf
Tx public key: f902bcb7dcbe58297ed790196896a37b313051e716fd97e8228a3650ab36eb23
Timestamp: 1629140916 Timestamp [UCT]: 2021-08-16 19:08:36 Age [y:d:h:m:s]: 03:272:20:20:05
Block: 315479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 968067 RingCT/type: yes/0
Extra: 01f902bcb7dcbe58297ed790196896a37b313051e716fd97e8228a3650ab36eb23021100000033e6f80b5a000000000000000000

1 output(s) for total of 55.297698593000 dcy

stealth address amount amount idx
00: f705e02b90427cbf6f67ba3e6eee35ed4a9c976631d5ba069d16d61524bf89c1 55.297698593000 656592 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": 315489, "vin": [ { "gen": { "height": 315479 } } ], "vout": [ { "amount": 55297698593, "target": { "key": "f705e02b90427cbf6f67ba3e6eee35ed4a9c976631d5ba069d16d61524bf89c1" } } ], "extra": [ 1, 249, 2, 188, 183, 220, 190, 88, 41, 126, 215, 144, 25, 104, 150, 163, 123, 49, 48, 81, 231, 22, 253, 151, 232, 34, 138, 54, 80, 171, 54, 235, 35, 2, 17, 0, 0, 0, 51, 230, 248, 11, 90, 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