Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395bef6ea079b4bf4426e93ebcdfc628548767230a5c5ddd4a556634d35b168f

Tx prefix hash: f7e5a5205f89078e2de9f9f9d30131f8c6c1efbd00305fd8c4ed3349b3b96f5d
Tx public key: b09d9736dedde5f88bc67db914b4bd283aeddefa4369d4af77a45bb98c5cff3c
Timestamp: 1699844597 Timestamp [UCT]: 2023-11-13 03:03:17 Age [y:d:h:m:s]: 01:192:18:29:40
Block: 890462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398995 RingCT/type: yes/0
Extra: 01b09d9736dedde5f88bc67db914b4bd283aeddefa4369d4af77a45bb98c5cff3c02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.687907023000 dcy

stealth address amount amount idx
00: 1aa63f8fd9dbe3dea8c29c32db1d31d83578fde2e5cde360d2cbc1b7ffff4738 0.687907023000 1346485 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": 890472, "vin": [ { "gen": { "height": 890462 } } ], "vout": [ { "amount": 687907023, "target": { "key": "1aa63f8fd9dbe3dea8c29c32db1d31d83578fde2e5cde360d2cbc1b7ffff4738" } } ], "extra": [ 1, 176, 157, 151, 54, 222, 221, 229, 248, 139, 198, 125, 185, 20, 180, 189, 40, 58, 237, 222, 250, 67, 105, 212, 175, 119, 164, 91, 185, 140, 92, 255, 60, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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