Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f07106d931b58149141fca6dafa992a7960c5ef32c70f37aa2b0d5bbb3b13c9

Tx prefix hash: ab337eb510977f4fbb1cd5d7045d49ec3abfe0877bb5bf98786d27d83170ce12
Tx public key: c8eac5a87cdbe7b76cab4fb3b814f8f571b5c8b2e70a12ab96282e808e445121
Timestamp: 1580676285 Timestamp [UCT]: 2020-02-02 20:44:45 Age [y:d:h:m:s]: 04:300:01:02:44
Block: 57226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105881 RingCT/type: yes/0
Extra: 01c8eac5a87cdbe7b76cab4fb3b814f8f571b5c8b2e70a12ab96282e808e44512102110000000a4ac5aa02000000000000000000

1 output(s) for total of 396.640215406000 dcy

stealth address amount amount idx
00: 8b028cbd34b8c68c530deb879b9b2e4fbafd791641a1bfadb3c8633630c5783f 396.640215406000 105623 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": 57236, "vin": [ { "gen": { "height": 57226 } } ], "vout": [ { "amount": 396640215406, "target": { "key": "8b028cbd34b8c68c530deb879b9b2e4fbafd791641a1bfadb3c8633630c5783f" } } ], "extra": [ 1, 200, 234, 197, 168, 124, 219, 231, 183, 108, 171, 79, 179, 184, 20, 248, 245, 113, 181, 200, 178, 231, 10, 18, 171, 150, 40, 46, 128, 142, 68, 81, 33, 2, 17, 0, 0, 0, 10, 74, 197, 170, 2, 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