Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8709a5830ea3d81809f25d99af366e6cf8c46caa180d8245879fc48a53888ea3

Tx prefix hash: 27f1fdc7fbdf4d3718f3e1507dfee02a97718547a22897563e97eb80dd773262
Tx public key: 0e423ba2f378c36e6851de08d4edbb5d1b4b532a747541999261b67d3079a53e
Timestamp: 1703225211 Timestamp [UCT]: 2023-12-22 06:06:51 Age [y:d:h:m:s]: 01:324:02:27:55
Block: 918480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490485 RingCT/type: yes/0
Extra: 010e423ba2f378c36e6851de08d4edbb5d1b4b532a747541999261b67d3079a53e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d4a648890448d63973dd9f7736aa64e9f5c076345ef56c1bf2e4bb4f9f88b7b 0.600000000000 1376124 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": 918490, "vin": [ { "gen": { "height": 918480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d4a648890448d63973dd9f7736aa64e9f5c076345ef56c1bf2e4bb4f9f88b7b" } } ], "extra": [ 1, 14, 66, 59, 162, 243, 120, 195, 110, 104, 81, 222, 8, 212, 237, 187, 93, 27, 75, 83, 42, 116, 117, 65, 153, 146, 97, 182, 125, 48, 121, 165, 62, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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