Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce7ef1fca8aa9a97f14e97be682effc9c2e9bef0587666a86ef4e6a01100db81

Tx prefix hash: 93e8d0460edeee0e7fe7dad4fb4072f20e7e3c26508613ec2eef84efcd0bd38a
Tx public key: 5d3b0f3279e58dbe3c4254c57dcc26920fc25085188cfc089c9f0a49aa689c2c
Timestamp: 1763062835 Timestamp [UCT]: 2025-11-13 19:40:35 Age [y:d:h:m:s]: 00:047:21:05:39
Block: 1411434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34290 RingCT/type: yes/0
Extra: 015d3b0f3279e58dbe3c4254c57dcc26920fc25085188cfc089c9f0a49aa689c2c0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 102b5f379224195bbab26f82b7436dc66744b45a3bc19bab576e7c8fa3847f1c 0.600000000000 1899895 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": 1411444, "vin": [ { "gen": { "height": 1411434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "102b5f379224195bbab26f82b7436dc66744b45a3bc19bab576e7c8fa3847f1c" } } ], "extra": [ 1, 93, 59, 15, 50, 121, 229, 141, 190, 60, 66, 84, 197, 125, 204, 38, 146, 15, 194, 80, 133, 24, 140, 252, 8, 156, 159, 10, 73, 170, 104, 156, 44, 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