Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b25c30ffecef76ce4b022344948b65d414a0fb334b05bc8141e15720d9f0191

Tx prefix hash: 5b96f16107913c9d11d848d2341b258de8d76dee402a20f9d3d2d71063ea93c2
Tx public key: 05e92e84d8ba180683e8fddec801e30a38aaabb7d3c8f0f9bebea25389d5db14
Timestamp: 1704351270 Timestamp [UCT]: 2024-01-04 06:54:30 Age [y:d:h:m:s]: 01:322:17:40:43
Block: 927824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489486 RingCT/type: yes/0
Extra: 0105e92e84d8ba180683e8fddec801e30a38aaabb7d3c8f0f9bebea25389d5db14021100000012e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1eb4afee10ea3e451a2953cef37980eed8140e210aa426f160e9ae8f8171b5f2 0.600000000000 1385660 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": 927834, "vin": [ { "gen": { "height": 927824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1eb4afee10ea3e451a2953cef37980eed8140e210aa426f160e9ae8f8171b5f2" } } ], "extra": [ 1, 5, 233, 46, 132, 216, 186, 24, 6, 131, 232, 253, 222, 200, 1, 227, 10, 56, 170, 171, 183, 211, 200, 240, 249, 190, 190, 162, 83, 137, 213, 219, 20, 2, 17, 0, 0, 0, 18, 228, 187, 107, 131, 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