Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69edc02f338c40633f8e8c217540436478d90ca29434e0493e37030ef5baff08

Tx prefix hash: 609a9dca17a634fb405c20b720cc2db9c6733b773cf6c5c8f31f0f8616aaec8b
Tx public key: a948d71008c6c961248b27afd2c8dc81512bf5b5b0633e12d7325076b27699ea
Timestamp: 1745637930 Timestamp [UCT]: 2025-04-26 03:25:30 Age [y:d:h:m:s]: 00:209:10:43:40
Block: 1269588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147407 RingCT/type: yes/0
Extra: 01a948d71008c6c961248b27afd2c8dc81512bf5b5b0633e12d7325076b27699ea02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a83d07904af01e92ffad66250ac0d6d20ef24f8e911fce816fbb05965009aaa 0.600000000000 1756827 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": 1269598, "vin": [ { "gen": { "height": 1269588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a83d07904af01e92ffad66250ac0d6d20ef24f8e911fce816fbb05965009aaa" } } ], "extra": [ 1, 169, 72, 215, 16, 8, 198, 201, 97, 36, 139, 39, 175, 210, 200, 220, 129, 81, 43, 245, 181, 176, 99, 62, 18, 215, 50, 80, 118, 178, 118, 153, 234, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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