Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a0bef65ecead95379a516d5a3f1e57810c63c31e23d143cbfe5db1978a42918

Tx prefix hash: a9cd94453a50d35a2eba02f70a988d55b52b58b1e09dfe427127ff8e2f99f8c6
Tx public key: ab34c8f266e35d03b5e7be79f6651ab4ad81e2154829321a93cf7219d7d5540f
Timestamp: 1705159640 Timestamp [UCT]: 2024-01-13 15:27:20 Age [y:d:h:m:s]: 01:303:09:11:03
Block: 934505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475660 RingCT/type: yes/0
Extra: 01ab34c8f266e35d03b5e7be79f6651ab4ad81e2154829321a93cf7219d7d5540f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0c51ec0205b0463d1e54dc42aa54977266388e6855af38612676d17cd755e4c 0.600000000000 1392519 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": 934515, "vin": [ { "gen": { "height": 934505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0c51ec0205b0463d1e54dc42aa54977266388e6855af38612676d17cd755e4c" } } ], "extra": [ 1, 171, 52, 200, 242, 102, 227, 93, 3, 181, 231, 190, 121, 246, 101, 26, 180, 173, 129, 226, 21, 72, 41, 50, 26, 147, 207, 114, 25, 215, 213, 84, 15, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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