Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa9204f540c721835250e767e4f11df34038daaf088d879559b790798d5cdf8c

Tx prefix hash: ec916a92ca39b976dec352ff47a20bfd6da5909f186ba64e968746d55ebe7ecd
Tx public key: bfd01f4a1db2ec9f397f9b0dbf77b794892bddef3283324cf7b15a9787f0299b
Timestamp: 1744096649 Timestamp [UCT]: 2025-04-08 07:17:29 Age [y:d:h:m:s]: 00:299:07:49:52
Block: 1256820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211585 RingCT/type: yes/0
Extra: 01bfd01f4a1db2ec9f397f9b0dbf77b794892bddef3283324cf7b15a9787f0299b021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6da4b37d8984ef7d081d3faafcf1e06e4e41d1f9ed4f0dda99ad6e189b5be181 0.600000000000 1743937 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": 1256830, "vin": [ { "gen": { "height": 1256820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6da4b37d8984ef7d081d3faafcf1e06e4e41d1f9ed4f0dda99ad6e189b5be181" } } ], "extra": [ 1, 191, 208, 31, 74, 29, 178, 236, 159, 57, 127, 155, 13, 191, 119, 183, 148, 137, 43, 221, 239, 50, 131, 50, 76, 247, 177, 90, 151, 135, 240, 41, 155, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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