Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1853b296303364a5024d82f2f68ffaa96e8cb0a9f2f0eae5a82b1efef561ca5

Tx prefix hash: f34ef3601ef24e65338eb8f159e81ce949117f29e6ff19bec68a1a2b3cf9f7eb
Tx public key: 28594623f96dcbcc10e21c9addc0aed5f5cbf04d67f03c17519cb6a8274dcb36
Timestamp: 1683676944 Timestamp [UCT]: 2023-05-10 00:02:24 Age [y:d:h:m:s]: 02:042:00:42:20
Block: 756670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552044 RingCT/type: yes/0
Extra: 0128594623f96dcbcc10e21c9addc0aed5f5cbf04d67f03c17519cb6a8274dcb36021100000002b3164c24000000000000000000

1 output(s) for total of 1.909142627000 dcy

stealth address amount amount idx
00: e6bf5c8782c5faa3e6be95c4272fb64e06a0e5b0bf0e9d4d82f91679312e594b 1.909142627000 1205057 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": 756680, "vin": [ { "gen": { "height": 756670 } } ], "vout": [ { "amount": 1909142627, "target": { "key": "e6bf5c8782c5faa3e6be95c4272fb64e06a0e5b0bf0e9d4d82f91679312e594b" } } ], "extra": [ 1, 40, 89, 70, 35, 249, 109, 203, 204, 16, 226, 28, 154, 221, 192, 174, 213, 245, 203, 240, 77, 103, 240, 60, 23, 81, 156, 182, 168, 39, 77, 203, 54, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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