Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c139bea43d69283fbd6269575629ac4634d1bdaea7de0cef1dc1ba0cd3d08810

Tx prefix hash: 2c2752c3e599667d70303e08409a9e27b69d0377fd808436925372dafe778298
Tx public key: a911bb318e7cb6019ce9bc92231bf46a310d378445bb9285d06417efc0a8cab9
Timestamp: 1763022256 Timestamp [UCT]: 2025-11-13 08:24:16 Age [y:d:h:m:s]: 00:056:07:17:37
Block: 1411107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40312 RingCT/type: yes/0
Extra: 01a911bb318e7cb6019ce9bc92231bf46a310d378445bb9285d06417efc0a8cab9021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 131babd4b0502a8bc18ea6f6ae02d9830ccdb9b6b60e2674a51f1c2b669bbbda 0.600000000000 1899564 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": 1411117, "vin": [ { "gen": { "height": 1411107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "131babd4b0502a8bc18ea6f6ae02d9830ccdb9b6b60e2674a51f1c2b669bbbda" } } ], "extra": [ 1, 169, 17, 187, 49, 142, 124, 182, 1, 156, 233, 188, 146, 35, 27, 244, 106, 49, 13, 55, 132, 69, 187, 146, 133, 208, 100, 23, 239, 192, 168, 202, 185, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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