Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 703b25fc4c5e22d09b7c4caddb3b88b4a9e61a57230fcf04fab27115f6325318

Tx prefix hash: 2bda110ff2ce103450f78a70de48d80085006faec35368dd4cfbd8e4d64bb0e8
Tx public key: ea888e7e16af7100599f4e2f3ffcace5f82f716d5b3a583b33e75dc47cf62bc0
Timestamp: 1706119657 Timestamp [UCT]: 2024-01-24 18:07:37 Age [y:d:h:m:s]: 01:076:10:14:02
Block: 942453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315723 RingCT/type: yes/0
Extra: 01ea888e7e16af7100599f4e2f3ffcace5f82f716d5b3a583b33e75dc47cf62bc002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d5e58125576452a7494c4542d4e3043c9c64fed464ed6d4a0ebc5063942711f 0.600000000000 1400625 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": 942463, "vin": [ { "gen": { "height": 942453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d5e58125576452a7494c4542d4e3043c9c64fed464ed6d4a0ebc5063942711f" } } ], "extra": [ 1, 234, 136, 142, 126, 22, 175, 113, 0, 89, 159, 78, 47, 63, 252, 172, 229, 248, 47, 113, 109, 91, 58, 88, 59, 51, 231, 93, 196, 124, 246, 43, 192, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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