Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d36426da26378df67408985472b2ee02251bf1e27ed4ca71b273a5af07421b8

Tx prefix hash: fc29842b1025e98633d96ca69810384894dec372bfb1e87bcc9cefddd1c598d0
Tx public key: 98a381171d1808d77c6513e5e6faf0bc836fe1fdcb2d0777dfcc8b357243a436
Timestamp: 1755184251 Timestamp [UCT]: 2025-08-14 15:10:51 Age [y:d:h:m:s]: 00:098:23:50:04
Block: 1346729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70291 RingCT/type: yes/0
Extra: 0198a381171d1808d77c6513e5e6faf0bc836fe1fdcb2d0777dfcc8b357243a4360211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed8bccb4a9c0d2aed2d3d8abf41f1cd3b45ae28ce76c48ad4ad136f9fdc3bb1f 0.600000000000 1834632 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": 1346739, "vin": [ { "gen": { "height": 1346729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed8bccb4a9c0d2aed2d3d8abf41f1cd3b45ae28ce76c48ad4ad136f9fdc3bb1f" } } ], "extra": [ 1, 152, 163, 129, 23, 29, 24, 8, 215, 124, 101, 19, 229, 230, 250, 240, 188, 131, 111, 225, 253, 203, 45, 7, 119, 223, 204, 139, 53, 114, 67, 164, 54, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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