Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32103a793deaa34cf33d869bd1e87954c7ae950c76122f2dae39f7821d2f273a

Tx prefix hash: 1677461392e95bb926499bd01201cfce75a6575ae19af60ea8e963a0719d577c
Tx public key: e3316d00572e3345fecd310152b6e26e87c7e0d4d5c8899935d6edcd3f9a6d87
Timestamp: 1657263631 Timestamp [UCT]: 2022-07-08 07:00:31 Age [y:d:h:m:s]: 02:219:09:32:58
Block: 539151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 677906 RingCT/type: yes/0
Extra: 01e3316d00572e3345fecd310152b6e26e87c7e0d4d5c8899935d6edcd3f9a6d87021100000002bf7ee4e7000000000000000000

1 output(s) for total of 10.036194584000 dcy

stealth address amount amount idx
00: b55aafc034824977fc1b4e1c440f1b9acee9b3f58c901e5613eccffca16289b6 10.036194584000 969224 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": 539161, "vin": [ { "gen": { "height": 539151 } } ], "vout": [ { "amount": 10036194584, "target": { "key": "b55aafc034824977fc1b4e1c440f1b9acee9b3f58c901e5613eccffca16289b6" } } ], "extra": [ 1, 227, 49, 109, 0, 87, 46, 51, 69, 254, 205, 49, 1, 82, 182, 226, 110, 135, 199, 224, 212, 213, 200, 137, 153, 53, 214, 237, 205, 63, 154, 109, 135, 2, 17, 0, 0, 0, 2, 191, 126, 228, 231, 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