Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c1695ccb9de44bfb58a43a94ebc9e000f6148e6497640fb132f71cf9405d226

Tx prefix hash: b5c48870d3c7b6c059bd59cd79ffe7c69695997f23c048ce243e4341e7736614
Tx public key: a7017e2ee85cb8b5b3fd7b87c15ddc7b7056343f03b7da6e83fde8f0354af4ca
Timestamp: 1761603792 Timestamp [UCT]: 2025-10-27 22:23:12 Age [y:d:h:m:s]: 00:097:14:54:42
Block: 1399365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69703 RingCT/type: yes/0
Extra: 01a7017e2ee85cb8b5b3fd7b87c15ddc7b7056343f03b7da6e83fde8f0354af4ca0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbc9fd2eb64629432592a553c570327322b2569638003148ba39df50b013c4f6 0.600000000000 1887670 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": 1399375, "vin": [ { "gen": { "height": 1399365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbc9fd2eb64629432592a553c570327322b2569638003148ba39df50b013c4f6" } } ], "extra": [ 1, 167, 1, 126, 46, 232, 92, 184, 181, 179, 253, 123, 135, 193, 93, 220, 123, 112, 86, 52, 63, 3, 183, 218, 110, 131, 253, 232, 240, 53, 74, 244, 202, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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