Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6997d015719a3e992935976b9e62bf4a383b61ba254033d78bd0c6ac5445b9b

Tx prefix hash: e1f452d9c476700f295aff9ea1fe58d784a44a96f3a23f73c41fb97a5f3db122
Tx public key: 4cabb32f677bed957dd8e32751080c83f29c49f10fa6b6cb1fd9e5fd8acfbe9a
Timestamp: 1699407461 Timestamp [UCT]: 2023-11-08 01:37:41 Age [y:d:h:m:s]: 01:358:01:28:24
Block: 886836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514817 RingCT/type: yes/0
Extra: 014cabb32f677bed957dd8e32751080c83f29c49f10fa6b6cb1fd9e5fd8acfbe9a021100000002faf35c9c000000000000000000

1 output(s) for total of 0.707203158000 dcy

stealth address amount amount idx
00: 6d89e6b5b6df9af64f1c3831d95abcd40c11d843f6becd3e79a6fd9339f976f9 0.707203158000 1342683 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": 886846, "vin": [ { "gen": { "height": 886836 } } ], "vout": [ { "amount": 707203158, "target": { "key": "6d89e6b5b6df9af64f1c3831d95abcd40c11d843f6becd3e79a6fd9339f976f9" } } ], "extra": [ 1, 76, 171, 179, 47, 103, 123, 237, 149, 125, 216, 227, 39, 81, 8, 12, 131, 242, 156, 73, 241, 15, 166, 182, 203, 31, 217, 229, 253, 138, 207, 190, 154, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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