Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e24fb3815cf0ad740ecf50a3562c2af529d02e64d1bae2eb658ac6a57bd3d8a

Tx prefix hash: ad5c291b189a1e2b676e7a4ed431ddb34a9a39e058dd505de1afa6211726da10
Tx public key: 669f84efd6ea938d4ef3f3c4a4072cfa757b0aab08d7525eb49160f2a0cb829a
Timestamp: 1706527545 Timestamp [UCT]: 2024-01-29 11:25:45 Age [y:d:h:m:s]: 01:099:19:20:07
Block: 945845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332425 RingCT/type: yes/0
Extra: 01669f84efd6ea938d4ef3f3c4a4072cfa757b0aab08d7525eb49160f2a0cb829a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64d43abebb5eb123cf52f2974578b2abb08b5a23461e0b50bd6397377f0793ab 0.600000000000 1404169 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": 945855, "vin": [ { "gen": { "height": 945845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64d43abebb5eb123cf52f2974578b2abb08b5a23461e0b50bd6397377f0793ab" } } ], "extra": [ 1, 102, 159, 132, 239, 214, 234, 147, 141, 78, 243, 243, 196, 164, 7, 44, 250, 117, 123, 10, 171, 8, 215, 82, 94, 180, 145, 96, 242, 160, 203, 130, 154, 2, 17, 0, 0, 0, 2, 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