Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a0d100e9c49225a5b23a28dba2151ce6742c3d99cc538e096547d95e906ac41

Tx prefix hash: 571b669595919e1c4ced84514c1a43cd43cb07e5adf015e9cb4601400a0d6622
Tx public key: 8b6f2874a3561aa855d7467cbd9f25c063e6ef41a2e86c024fa340cee8fe6af1
Timestamp: 1708384462 Timestamp [UCT]: 2024-02-19 23:14:22 Age [y:d:h:m:s]: 01:048:10:25:19
Block: 961257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295632 RingCT/type: yes/0
Extra: 018b6f2874a3561aa855d7467cbd9f25c063e6ef41a2e86c024fa340cee8fe6af102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53040a46f0f861f1b96a7bb61946c71b85e69d987d6d858cba56143ef9b21407 0.600000000000 1420866 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": 961267, "vin": [ { "gen": { "height": 961257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53040a46f0f861f1b96a7bb61946c71b85e69d987d6d858cba56143ef9b21407" } } ], "extra": [ 1, 139, 111, 40, 116, 163, 86, 26, 168, 85, 215, 70, 124, 189, 159, 37, 192, 99, 230, 239, 65, 162, 232, 108, 2, 79, 163, 64, 206, 232, 254, 106, 241, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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