Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da364f40c9a8f81bc682dfca48bb3ae28b98cc1d98d71acf682843f8f01d8136

Tx prefix hash: fbd1e45f4a5f3121ebdb9690e16b879953517791c4582796cce708abb69f8a7b
Tx public key: d39dd78fd0c2d6bd2d54e9da9d0810682419856d38d97eed41bd6a84abd5bd7e
Timestamp: 1755141409 Timestamp [UCT]: 2025-08-14 03:16:49 Age [y:d:h:m:s]: 00:098:10:45:39
Block: 1346447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69829 RingCT/type: yes/0
Extra: 01d39dd78fd0c2d6bd2d54e9da9d0810682419856d38d97eed41bd6a84abd5bd7e021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 370dd70f59f97afaeadd3f816e838e994f9017f7524c0ca4f96e6831d6319332 0.600000000000 1834348 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": 1346457, "vin": [ { "gen": { "height": 1346447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "370dd70f59f97afaeadd3f816e838e994f9017f7524c0ca4f96e6831d6319332" } } ], "extra": [ 1, 211, 157, 215, 143, 208, 194, 214, 189, 45, 84, 233, 218, 157, 8, 16, 104, 36, 25, 133, 109, 56, 217, 126, 237, 65, 189, 106, 132, 171, 213, 189, 126, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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