Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b10ffe9316ad721f94f5734b0ce1d8d3fe8de0ca2ddcdf7137a664a86059c952

Tx prefix hash: 643620f4ea4c7eece160c9bdcacf2d20fe7327fa66df5afdc0de1908baa9746a
Tx public key: b1075a56ae2e46cd20a118f6209d6152ce85af02d163dfdb2b6a2e402d75baa6
Timestamp: 1736067814 Timestamp [UCT]: 2025-01-05 09:03:34 Age [y:d:h:m:s]: 00:127:18:48:49
Block: 1190642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91117 RingCT/type: yes/0
Extra: 01b1075a56ae2e46cd20a118f6209d6152ce85af02d163dfdb2b6a2e402d75baa60211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ba0039ae6ac851d3112c46a8f8adcf6c48d9b7b59e893e91ff43bcacfe997e5 0.600000000000 1677159 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": 1190652, "vin": [ { "gen": { "height": 1190642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ba0039ae6ac851d3112c46a8f8adcf6c48d9b7b59e893e91ff43bcacfe997e5" } } ], "extra": [ 1, 177, 7, 90, 86, 174, 46, 70, 205, 32, 161, 24, 246, 32, 157, 97, 82, 206, 133, 175, 2, 209, 99, 223, 219, 43, 106, 46, 64, 45, 117, 186, 166, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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