Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7aa8adc52bea8de9d86ba3eba0a22eac38bb4cecc570d6aff567d3cf83c85fc

Tx prefix hash: b69e77e646eab01f839399849eba4d16dd4cfaa5f8f3c12e9f1d95af6337aee5
Tx public key: 0c39882e0af72179783730665fc3ef00bde69dd33340d081aa9e08cb0fafbb7e
Timestamp: 1718468309 Timestamp [UCT]: 2024-06-15 16:18:29 Age [y:d:h:m:s]: 00:274:20:31:01
Block: 1044870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196412 RingCT/type: yes/0
Extra: 010c39882e0af72179783730665fc3ef00bde69dd33340d081aa9e08cb0fafbb7e021100000001befa2d88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 712f55ca34c74238b5e36a765e89a2bad8173e041b5c7c4abdd4dc87b78c839b 0.600000000000 1514295 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": 1044880, "vin": [ { "gen": { "height": 1044870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "712f55ca34c74238b5e36a765e89a2bad8173e041b5c7c4abdd4dc87b78c839b" } } ], "extra": [ 1, 12, 57, 136, 46, 10, 247, 33, 121, 120, 55, 48, 102, 95, 195, 239, 0, 189, 230, 157, 211, 51, 64, 208, 129, 170, 158, 8, 203, 15, 175, 187, 126, 2, 17, 0, 0, 0, 1, 190, 250, 45, 136, 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