Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c08273d8dbe0baff718fa2e4ccf4692ce2efe43f2e2b1e405eb99cfa2472d39

Tx prefix hash: 5c2c41df73d2104a1cd52de356698d511eca61c35b89b428a43a49fe90ce2cec
Tx public key: 29bca7b05240e71a07906043a290bbe8eeeb8539040f9a21ea46f2ef803016ae
Timestamp: 1701001582 Timestamp [UCT]: 2023-11-26 12:26:22 Age [y:d:h:m:s]: 01:170:20:02:40
Block: 900044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383291 RingCT/type: yes/0
Extra: 0129bca7b05240e71a07906043a290bbe8eeeb8539040f9a21ea46f2ef803016ae021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.639411710000 dcy

stealth address amount amount idx
00: d61e98e06eeda2e4f9305740d15cbb5fd077a317f4cde52208c8c3f347ed411c 0.639411710000 1356521 of 0

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": 900054, "vin": [ { "gen": { "height": 900044 } } ], "vout": [ { "amount": 639411710, "target": { "key": "d61e98e06eeda2e4f9305740d15cbb5fd077a317f4cde52208c8c3f347ed411c" } } ], "extra": [ 1, 41, 188, 167, 176, 82, 64, 231, 26, 7, 144, 96, 67, 162, 144, 187, 232, 238, 235, 133, 57, 4, 15, 154, 33, 234, 70, 242, 239, 128, 48, 22, 174, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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