Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29430a0df061bb19d3705d793f24e69baa17b5803452709920629e0b977a4834

Tx prefix hash: f037259a24a3589225dffb063016502e5946f49254048bdb265d11639d36f923
Tx public key: b1a3a63366976d31f71a0e0f484642aa149523d29e1ac5fc3b259c7d440e89fb
Timestamp: 1716092958 Timestamp [UCT]: 2024-05-19 04:29:18 Age [y:d:h:m:s]: 00:303:13:22:30
Block: 1025164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216978 RingCT/type: yes/0
Extra: 01b1a3a63366976d31f71a0e0f484642aa149523d29e1ac5fc3b259c7d440e89fb02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 040cd5d68cbee634074f9dbfbbe70c76dc07bf33ff36f97ca3b74f8af4b78e07 0.600000000000 1491463 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": 1025174, "vin": [ { "gen": { "height": 1025164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "040cd5d68cbee634074f9dbfbbe70c76dc07bf33ff36f97ca3b74f8af4b78e07" } } ], "extra": [ 1, 177, 163, 166, 51, 102, 151, 109, 49, 247, 26, 14, 15, 72, 70, 66, 170, 20, 149, 35, 210, 158, 26, 197, 252, 59, 37, 156, 125, 68, 14, 137, 251, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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