Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b46f975f0550256a8dcd773f313cedac54c3d12805abb833d54483dd7d5ca04

Tx prefix hash: f2b41d38e90e9d200d7f44c7cce175b6e5ef3f100561639a4b30cd96bce8028e
Tx public key: 0efd544247d7633f7ce83ee0937af0a47b6df30ce1511bea5d4454d916e30d43
Timestamp: 1714243094 Timestamp [UCT]: 2024-04-27 18:38:14 Age [y:d:h:m:s]: 00:323:17:52:40
Block: 1009830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231439 RingCT/type: yes/0
Extra: 010efd544247d7633f7ce83ee0937af0a47b6df30ce1511bea5d4454d916e30d430211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7a7aebda678638f0cbf419b287c6ba97c75c29164076e419f2bd40f3bf72138 0.600000000000 1471610 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": 1009840, "vin": [ { "gen": { "height": 1009830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7a7aebda678638f0cbf419b287c6ba97c75c29164076e419f2bd40f3bf72138" } } ], "extra": [ 1, 14, 253, 84, 66, 71, 215, 99, 63, 124, 232, 62, 224, 147, 122, 240, 164, 123, 109, 243, 12, 225, 81, 27, 234, 93, 68, 84, 217, 22, 227, 13, 67, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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