Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59a56275ab52e0bad13b397d7b35024702c98b6706eccde63ebd42d01c7c8b75

Tx prefix hash: 09faf013f7799648a57c6f4749934a766cd8a378120c8be250a33fe3944e231c
Tx public key: 0a694672158165da7020a2ecb9e2d5139260b8646c2ae4e4ca8593ba1fbbf0fb
Timestamp: 1694262993 Timestamp [UCT]: 2023-09-09 12:36:33 Age [y:d:h:m:s]: 01:173:10:45:38
Block: 844360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385044 RingCT/type: yes/0
Extra: 010a694672158165da7020a2ecb9e2d5139260b8646c2ae4e4ca8593ba1fbbf0fb02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.977878448000 dcy

stealth address amount amount idx
00: d8fa7948c9eeec91cfad7a926dbc7c7382944a36b04e7d986279ea23758651be 0.977878448000 1297664 of 0

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": 844370, "vin": [ { "gen": { "height": 844360 } } ], "vout": [ { "amount": 977878448, "target": { "key": "d8fa7948c9eeec91cfad7a926dbc7c7382944a36b04e7d986279ea23758651be" } } ], "extra": [ 1, 10, 105, 70, 114, 21, 129, 101, 218, 112, 32, 162, 236, 185, 226, 213, 19, 146, 96, 184, 100, 108, 42, 228, 228, 202, 133, 147, 186, 31, 187, 240, 251, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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