Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1ee69e1275dd03e1ee00511343a677dfc1d5c2e4e4266638b7ca5bb89a43229

Tx prefix hash: bd7e4eae18ad9336967ffbcbe25b9f2eb49e9cb1365826fd7b3984fed64c92df
Tx public key: f33c6e938d67064732e0d454a34c99ecabee239e328b0b3c97e44817b6ff6fdd
Timestamp: 1707983477 Timestamp [UCT]: 2024-02-15 07:51:17 Age [y:d:h:m:s]: 01:011:09:38:41
Block: 957928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269157 RingCT/type: yes/0
Extra: 01f33c6e938d67064732e0d454a34c99ecabee239e328b0b3c97e44817b6ff6fdd02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8072cd0a784cad76697664c25a79c82d761899ef3f0cedf1004d782fd02f198d 0.600000000000 1417279 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": 957938, "vin": [ { "gen": { "height": 957928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8072cd0a784cad76697664c25a79c82d761899ef3f0cedf1004d782fd02f198d" } } ], "extra": [ 1, 243, 60, 110, 147, 141, 103, 6, 71, 50, 224, 212, 84, 163, 76, 153, 236, 171, 238, 35, 158, 50, 139, 11, 60, 151, 228, 72, 23, 182, 255, 111, 221, 2, 17, 0, 0, 0, 5, 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