Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1993b943304bfa4e8aee1c9c5f61ff075c9e50311f0cd05dcc55b4c9bd446bd

Tx prefix hash: 997f1609e4d72d8abdbca10adc03179a394a2c60dd808b00c078d2ce7b92423a
Tx public key: d64402ab827581e92eb6e4a25881be27bbd66e555c7c4934bf94d19b8eb9957e
Timestamp: 1742392523 Timestamp [UCT]: 2025-03-19 13:55:23 Age [y:d:h:m:s]: 00:075:11:56:40
Block: 1242748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53985 RingCT/type: yes/0
Extra: 01d64402ab827581e92eb6e4a25881be27bbd66e555c7c4934bf94d19b8eb9957e021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4f3bb4abc3ce97a1f8b9b8667fedb5ef235e5a0262dfc92da46144b103c39b6 0.600000000000 1729725 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": 1242758, "vin": [ { "gen": { "height": 1242748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4f3bb4abc3ce97a1f8b9b8667fedb5ef235e5a0262dfc92da46144b103c39b6" } } ], "extra": [ 1, 214, 68, 2, 171, 130, 117, 129, 233, 46, 182, 228, 162, 88, 129, 190, 39, 187, 214, 110, 85, 92, 124, 73, 52, 191, 148, 209, 155, 142, 185, 149, 126, 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