Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4427583b68ed8e824b759a726c17decaec5fcd29881550db725bb0e580c3a00

Tx prefix hash: 66177d547ca19cb6159aad49b1d8cb9a06399a0a4a46514a96f7b58d525ae51f
Tx public key: 3e3641122e52ec6707ac4e29d97787c2a270f83aa7cb30a075d270f3953bad3c
Timestamp: 1737142657 Timestamp [UCT]: 2025-01-17 19:37:37 Age [y:d:h:m:s]: 00:058:15:44:42
Block: 1199531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41714 RingCT/type: yes/0
Extra: 013e3641122e52ec6707ac4e29d97787c2a270f83aa7cb30a075d270f3953bad3c0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d11ca0d07d6833e07898d2db31b2609f05dd1b7f5fc61476d02176fd2ebab5b 0.600000000000 1686162 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": 1199541, "vin": [ { "gen": { "height": 1199531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d11ca0d07d6833e07898d2db31b2609f05dd1b7f5fc61476d02176fd2ebab5b" } } ], "extra": [ 1, 62, 54, 65, 18, 46, 82, 236, 103, 7, 172, 78, 41, 217, 119, 135, 194, 162, 112, 248, 58, 167, 203, 48, 160, 117, 210, 112, 243, 149, 59, 173, 60, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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