Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d438e6e121260ac77751c3782ba9c4702f456ecd6ecc50f362c07c0ed65662dc

Tx prefix hash: 012f44626dbb59f6f75e3d9bc13dbbb5bc19609f81e51f09e82ee21e435d6f52
Tx public key: afceca957a1cb2f2dabefb6b9316ba82d56b17fefa34b9e6253f96ef3a1c43d5
Timestamp: 1751196010 Timestamp [UCT]: 2025-06-29 11:20:10 Age [y:d:h:m:s]: 00:193:19:45:39
Block: 1315164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136716 RingCT/type: yes/0
Extra: 01afceca957a1cb2f2dabefb6b9316ba82d56b17fefa34b9e6253f96ef3a1c43d502110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f40883f8df44d1fc09e490e1d274e5a0693f8f030865978c96a0cbf998b115d8 0.600000000000 1802817 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": 1315174, "vin": [ { "gen": { "height": 1315164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f40883f8df44d1fc09e490e1d274e5a0693f8f030865978c96a0cbf998b115d8" } } ], "extra": [ 1, 175, 206, 202, 149, 122, 28, 178, 242, 218, 190, 251, 107, 147, 22, 186, 130, 213, 107, 23, 254, 250, 52, 185, 230, 37, 63, 150, 239, 58, 28, 67, 213, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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