Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46e20aa1c92b1d0547ceaa9c85aac5642c8077e2a6fcb84d8ee083bf9e34082c

Tx prefix hash: e45ab4a013d7be32d68f25c574778937bb493f38114559abf6ca4999ce6f6c5a
Tx public key: 5d4edb8c656b10ca211ce890b3340ddbcc2561cec76f92786d4d5dccf6843ee6
Timestamp: 1737290603 Timestamp [UCT]: 2025-01-19 12:43:23 Age [y:d:h:m:s]: 00:152:07:35:23
Block: 1200716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108555 RingCT/type: yes/0
Extra: 015d4edb8c656b10ca211ce890b3340ddbcc2561cec76f92786d4d5dccf6843ee6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41150a6e4579adc3205046efe1b2f5f542276b9b0565e653e7615e6f269affff 0.600000000000 1687361 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": 1200726, "vin": [ { "gen": { "height": 1200716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41150a6e4579adc3205046efe1b2f5f542276b9b0565e653e7615e6f269affff" } } ], "extra": [ 1, 93, 78, 219, 140, 101, 107, 16, 202, 33, 28, 232, 144, 179, 52, 13, 219, 204, 37, 97, 206, 199, 111, 146, 120, 109, 77, 93, 204, 246, 132, 62, 230, 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