Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d3b63f938853de7c7b19eb669a71aa58027b26d5be2b0df19a04c3be60b6e38

Tx prefix hash: 7b35d25842a244a78340df6b1e157784e1c0f25e05432f49edee72880da5426c
Tx public key: e942ef2d98469d36b61b25efa71e9c780c136667c2a530862e34448b9c386111
Timestamp: 1704514536 Timestamp [UCT]: 2024-01-06 04:15:36 Age [y:d:h:m:s]: 01:304:16:03:05
Block: 929144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476579 RingCT/type: yes/0
Extra: 01e942ef2d98469d36b61b25efa71e9c780c136667c2a530862e34448b9c38611102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6d88bc491c59507fd3cbe23ae5232130e0c5cae0ee4c49af9f794db15f6df17 0.600000000000 1387012 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": 929154, "vin": [ { "gen": { "height": 929144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6d88bc491c59507fd3cbe23ae5232130e0c5cae0ee4c49af9f794db15f6df17" } } ], "extra": [ 1, 233, 66, 239, 45, 152, 70, 157, 54, 182, 27, 37, 239, 167, 30, 156, 120, 12, 19, 102, 103, 194, 165, 48, 134, 46, 52, 68, 139, 156, 56, 97, 17, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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