Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0ea0caf889b5da503f0fb3514e22ca2e22c81e0873bb1ad8872785dc0423bf7

Tx prefix hash: 15bc5ca14d526cae825e2946c8fc9e531f1ad394c63034d9089dbfecbdafe3a7
Tx public key: ed2faf51bc9988d776a6d8f4f86b7a1971ee61f41ba26eef8e2666ed11b03a07
Timestamp: 1727568942 Timestamp [UCT]: 2024-09-29 00:15:42 Age [y:d:h:m:s]: 00:056:17:19:47
Block: 1120306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40529 RingCT/type: yes/0
Extra: 01ed2faf51bc9988d776a6d8f4f86b7a1971ee61f41ba26eef8e2666ed11b03a07021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 847bbf86c8a2affa967bd2e8aca2905382216ccd64bf1f40a41f6a2ad90d1a7b 0.600000000000 1602175 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": 1120316, "vin": [ { "gen": { "height": 1120306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "847bbf86c8a2affa967bd2e8aca2905382216ccd64bf1f40a41f6a2ad90d1a7b" } } ], "extra": [ 1, 237, 47, 175, 81, 188, 153, 136, 215, 118, 166, 216, 244, 248, 107, 122, 25, 113, 238, 97, 244, 27, 162, 110, 239, 142, 38, 102, 237, 17, 176, 58, 7, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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