Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a251b6bd3bbbc0f39d5f2bfb48555f8698eed32517d85a182cd32c13a41b53a1

Tx prefix hash: db68793df166f92b945fa1f1a2d81ea1a26701a0ab24ad294e7445f724fe4db0
Tx public key: 66436a0f286ca0711cd42986d38a70410aee07088b563ff5cd3d8149f6c5e3b2
Timestamp: 1715594163 Timestamp [UCT]: 2024-05-13 09:56:03 Age [y:d:h:m:s]: 00:352:03:18:06
Block: 1021054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251687 RingCT/type: yes/0
Extra: 0166436a0f286ca0711cd42986d38a70410aee07088b563ff5cd3d8149f6c5e3b202110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 367438fff1f8d32addbc20ba943c44de47547c49c536ecd3b58eca3d8e2a5b2a 0.600000000000 1485231 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": 1021064, "vin": [ { "gen": { "height": 1021054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "367438fff1f8d32addbc20ba943c44de47547c49c536ecd3b58eca3d8e2a5b2a" } } ], "extra": [ 1, 102, 67, 106, 15, 40, 108, 160, 113, 28, 212, 41, 134, 211, 138, 112, 65, 10, 238, 7, 8, 139, 86, 63, 245, 205, 61, 129, 73, 246, 197, 227, 178, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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