Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa95ce60903b6f4bd96dfb49d94ebebfa602f91e4528aaccef6c5466a996c7c0

Tx prefix hash: 62cc7fba6c93827928ca5800d69b0c53ed50dc143b9022a47e6c4736ef986767
Tx public key: 626c0ef2136e4c6450541c1b9a5472231238cc39a2221dfc68128c3e4d8b6386
Timestamp: 1745556687 Timestamp [UCT]: 2025-04-25 04:51:27 Age [y:d:h:m:s]: 00:199:07:30:10
Block: 1268918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140160 RingCT/type: yes/0
Extra: 01626c0ef2136e4c6450541c1b9a5472231238cc39a2221dfc68128c3e4d8b6386021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4eb41823dab04ed99df533949f9ccf0e324c3aec0e2214aad3daabbcb2df3ea0 0.600000000000 1756151 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": 1268928, "vin": [ { "gen": { "height": 1268918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4eb41823dab04ed99df533949f9ccf0e324c3aec0e2214aad3daabbcb2df3ea0" } } ], "extra": [ 1, 98, 108, 14, 242, 19, 110, 76, 100, 80, 84, 28, 27, 154, 84, 114, 35, 18, 56, 204, 57, 162, 34, 29, 252, 104, 18, 140, 62, 77, 139, 99, 134, 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