Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9049144911affb2111a287cc10d93ca37f59ff49959b0172ac5f490487a347c

Tx prefix hash: 8f48d4216c0f57c89582de806e31399e989d56bb8cfb78108610388dc56d6b0c
Tx public key: ac20d3aea37ce8db8467a7a5c530aa7e7260c5a07e9eb03075b137e3a33e6324
Timestamp: 1710867267 Timestamp [UCT]: 2024-03-19 16:54:27 Age [y:d:h:m:s]: 01:000:03:03:43
Block: 981864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261062 RingCT/type: yes/0
Extra: 01ac20d3aea37ce8db8467a7a5c530aa7e7260c5a07e9eb03075b137e3a33e632402110000001152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79f05c29957007048d46157f3f5ca88ea58c103050a5c8ef6d284a5ab72b0973 0.600000000000 1441963 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": 981874, "vin": [ { "gen": { "height": 981864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79f05c29957007048d46157f3f5ca88ea58c103050a5c8ef6d284a5ab72b0973" } } ], "extra": [ 1, 172, 32, 211, 174, 163, 124, 232, 219, 132, 103, 167, 165, 197, 48, 170, 126, 114, 96, 197, 160, 126, 158, 176, 48, 117, 177, 55, 227, 163, 62, 99, 36, 2, 17, 0, 0, 0, 17, 82, 212, 126, 148, 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