Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b3c7e3c2308d173688c167b664d90a7b03c4c2608343eb5e7d61c809cb76acb

Tx prefix hash: 03d626e812c9b70c4f11a05bca02aa0352d2218ef864581af8b9efbf5b00b64e
Tx public key: 0023133827d9d31080994ff166db5fc63f495334aa831898be9d56ffc2b23d71
Timestamp: 1696624965 Timestamp [UCT]: 2023-10-06 20:42:45 Age [y:d:h:m:s]: 01:213:16:41:10
Block: 863977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413782 RingCT/type: yes/0
Extra: 010023133827d9d31080994ff166db5fc63f495334aa831898be9d56ffc2b23d71021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.841948604000 dcy

stealth address amount amount idx
00: 4f34403af865badc512922d0a0b5340c6b7a025b57f2c51bf865d62a9628eada 0.841948604000 1318481 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": 863987, "vin": [ { "gen": { "height": 863977 } } ], "vout": [ { "amount": 841948604, "target": { "key": "4f34403af865badc512922d0a0b5340c6b7a025b57f2c51bf865d62a9628eada" } } ], "extra": [ 1, 0, 35, 19, 56, 39, 217, 211, 16, 128, 153, 79, 241, 102, 219, 95, 198, 63, 73, 83, 52, 170, 131, 24, 152, 190, 157, 86, 255, 194, 178, 61, 113, 2, 17, 0, 0, 0, 5, 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