Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e645dccc82c32d1700e29acc09a96fb7a1873599659a505480ff9cee54784fbe

Tx prefix hash: 020c4cbd0202e8d4e53fab2628d5fa8733ca963af0af7268b0eb19f211cabb39
Tx public key: bb714ed7ff1787d0f8e13ae299fba084dfa3a842ada40c20e09f674bdea4feb0
Timestamp: 1766054405 Timestamp [UCT]: 2025-12-18 10:40:05 Age [y:d:h:m:s]: 00:005:04:07:20
Block: 1436232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3691 RingCT/type: yes/0
Extra: 01bb714ed7ff1787d0f8e13ae299fba084dfa3a842ada40c20e09f674bdea4feb0021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a88c115a260c8f64bf1cdece1fc6e56edcb6a084d2a1c6f1fab70780b32fc651 0.600000000000 1925037 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": 1436242, "vin": [ { "gen": { "height": 1436232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a88c115a260c8f64bf1cdece1fc6e56edcb6a084d2a1c6f1fab70780b32fc651" } } ], "extra": [ 1, 187, 113, 78, 215, 255, 23, 135, 208, 248, 225, 58, 226, 153, 251, 160, 132, 223, 163, 168, 66, 173, 164, 12, 32, 224, 159, 103, 75, 222, 164, 254, 176, 2, 17, 0, 0, 0, 6, 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