Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2c31483d78f20a77e7eaf382a9aaa0764f834c474e0d4da80135eb43158ef7f

Tx prefix hash: a883ecba1eb2d4033e49347e8aadbbb208d8757d46b6ddd1e098834b34f5d083
Tx public key: 19c8fc56efbffce7c8a7c28d2a8ffe53d2a1b232452a4da1548c844b43db68a2
Timestamp: 1681158184 Timestamp [UCT]: 2023-04-10 20:23:04 Age [y:d:h:m:s]: 01:277:17:16:15
Block: 735774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460003 RingCT/type: yes/0
Extra: 0119c8fc56efbffce7c8a7c28d2a8ffe53d2a1b232452a4da1548c844b43db68a20211000000015029cbac000000000000000000

1 output(s) for total of 2.239110506000 dcy

stealth address amount amount idx
00: c9c489bcb11a2076c5db2162d22ad2b23f407d8b2ad1ac62ae7803a2ac602fc8 2.239110506000 1182129 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": 735784, "vin": [ { "gen": { "height": 735774 } } ], "vout": [ { "amount": 2239110506, "target": { "key": "c9c489bcb11a2076c5db2162d22ad2b23f407d8b2ad1ac62ae7803a2ac602fc8" } } ], "extra": [ 1, 25, 200, 252, 86, 239, 191, 252, 231, 200, 167, 194, 141, 42, 143, 254, 83, 210, 161, 178, 50, 69, 42, 77, 161, 84, 140, 132, 75, 67, 219, 104, 162, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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