Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf96a80b8ef8c71bab8d49df1fa09055bf91b046bb1331119fcf55a5fe869a3a

Tx prefix hash: 52eaddcf14d61c72fdb76946d5c68cb7217921d9bcb0e2c6fb2e0745c7b51242
Tx public key: 8e3a3c955c7aa98c21c2bd4d08a7dcb1b54bd7ae5eed795767aeb179f705eaf6
Timestamp: 1729849755 Timestamp [UCT]: 2024-10-25 09:49:15 Age [y:d:h:m:s]: 00:235:06:16:32
Block: 1139178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167874 RingCT/type: yes/0
Extra: 018e3a3c955c7aa98c21c2bd4d08a7dcb1b54bd7ae5eed795767aeb179f705eaf60211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0c99fb3fb015f4ae2483ff71a3042624c450a11a96cd3e5b750626db5487896 0.600000000000 1622949 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": 1139188, "vin": [ { "gen": { "height": 1139178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0c99fb3fb015f4ae2483ff71a3042624c450a11a96cd3e5b750626db5487896" } } ], "extra": [ 1, 142, 58, 60, 149, 92, 122, 169, 140, 33, 194, 189, 77, 8, 167, 220, 177, 181, 75, 215, 174, 94, 237, 121, 87, 103, 174, 177, 121, 247, 5, 234, 246, 2, 17, 0, 0, 0, 1, 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