Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6e35c08ef69dc325c083dfe34d48e4fa99fcb4a9460375b38248999d17f817b

Tx prefix hash: 99a51ba4ae98912b15f76c2a626bf83d2d5fe334c8893432d58202543b426b97
Tx public key: 9e234cf986063dc95ae66d58ec5002a3ace2fec5a9ac5202c08580bd191d299a
Timestamp: 1738609723 Timestamp [UCT]: 2025-02-03 19:08:43 Age [y:d:h:m:s]: 00:288:19:03:51
Block: 1211405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204166 RingCT/type: yes/0
Extra: 019e234cf986063dc95ae66d58ec5002a3ace2fec5a9ac5202c08580bd191d299a021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b529a5eae25649c33b8ac60a823474f7d8b112e96b84ce350aaba197cf6b9c6 0.600000000000 1698166 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": 1211415, "vin": [ { "gen": { "height": 1211405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b529a5eae25649c33b8ac60a823474f7d8b112e96b84ce350aaba197cf6b9c6" } } ], "extra": [ 1, 158, 35, 76, 249, 134, 6, 61, 201, 90, 230, 109, 88, 236, 80, 2, 163, 172, 226, 254, 197, 169, 172, 82, 2, 192, 133, 128, 189, 25, 29, 41, 154, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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