Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dc8bfa3956348a0285e26f066040d216428176e141348c2a0b9f630d5066407

Tx prefix hash: d83f13daf98a2baec4a7a6396a9ee7ecc7f37e13c8cadf7ecf1b5485f14d2238
Tx public key: 0d1f40b90a7481f80be347cc4bf07a4ace81c7cefd5a7c108a04d0f903eef3b2
Timestamp: 1763469173 Timestamp [UCT]: 2025-11-18 12:32:53 Age [y:d:h:m:s]: 00:009:17:24:20
Block: 1414809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6966 RingCT/type: yes/0
Extra: 010d1f40b90a7481f80be347cc4bf07a4ace81c7cefd5a7c108a04d0f903eef3b2021100000002fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4421ee6e9d1b95925a3c8272d376fe365413b2b39aa328d9cbf81a0da9e5384 0.600000000000 1903302 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": 1414819, "vin": [ { "gen": { "height": 1414809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4421ee6e9d1b95925a3c8272d376fe365413b2b39aa328d9cbf81a0da9e5384" } } ], "extra": [ 1, 13, 31, 64, 185, 10, 116, 129, 248, 11, 227, 71, 204, 75, 240, 122, 74, 206, 129, 199, 206, 253, 90, 124, 16, 138, 4, 208, 249, 3, 238, 243, 178, 2, 17, 0, 0, 0, 2, 251, 143, 208, 137, 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