Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c158ce4a19b89ecf2e5ce62d49d7c1ded269858466e6621d8cb5dc1c19762eb

Tx prefix hash: f0a9bc8e680816f70e5c40468d40d9305db31cd4b3e186c413543533a7aa6555
Tx public key: 1c0623636e660247c5afa50e4bf969d3471316f7e075195aafcee2a5db5ae74b
Timestamp: 1657142404 Timestamp [UCT]: 2022-07-06 21:20:04 Age [y:d:h:m:s]: 03:135:15:51:00
Block: 538133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 876688 RingCT/type: yes/0
Extra: 011c0623636e660247c5afa50e4bf969d3471316f7e075195aafcee2a5db5ae74b02110000000d4da16a3a000000000000000000

1 output(s) for total of 10.114446721000 dcy

stealth address amount amount idx
00: e6922035f6808e8059b4c0bc24d350c98e0329cab4d66ec69e950c18222e8c03 10.114446721000 968096 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": 538143, "vin": [ { "gen": { "height": 538133 } } ], "vout": [ { "amount": 10114446721, "target": { "key": "e6922035f6808e8059b4c0bc24d350c98e0329cab4d66ec69e950c18222e8c03" } } ], "extra": [ 1, 28, 6, 35, 99, 110, 102, 2, 71, 197, 175, 165, 14, 75, 249, 105, 211, 71, 19, 22, 247, 224, 117, 25, 90, 175, 206, 226, 165, 219, 90, 231, 75, 2, 17, 0, 0, 0, 13, 77, 161, 106, 58, 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