Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0ae55e786ff0d071116b436cdfd630a41e28baec7761efae751161674e7c9e9

Tx prefix hash: 38b2820a51b3f228a672dc9c54e966fe140c14101e6aedad60802d5edb38260c
Tx public key: 0db25fb76be5df9f2c8bc1e4af7ed3beae4dacbedf68025d6ee12e973c6018a5
Timestamp: 1724662017 Timestamp [UCT]: 2024-08-26 08:46:57 Age [y:d:h:m:s]: 00:261:04:13:10
Block: 1096203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186562 RingCT/type: yes/0
Extra: 010db25fb76be5df9f2c8bc1e4af7ed3beae4dacbedf68025d6ee12e973c6018a502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72a6948a75aaeda15e3f6e71f6546f8a30cac5737652a6fffa6875e35befa64a 0.600000000000 1571390 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": 1096213, "vin": [ { "gen": { "height": 1096203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72a6948a75aaeda15e3f6e71f6546f8a30cac5737652a6fffa6875e35befa64a" } } ], "extra": [ 1, 13, 178, 95, 183, 107, 229, 223, 159, 44, 139, 193, 228, 175, 126, 211, 190, 174, 77, 172, 190, 223, 104, 2, 93, 110, 225, 46, 151, 60, 96, 24, 165, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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