Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a979aeb2f5a70013368dac9b9a71e5380771649557d6f0a1a361e7f6003af46

Tx prefix hash: 5cdab599ee9153b9ccabccdf4511c1d7f999bef8082532e530323e637f5cd7f3
Tx public key: d2a2252dda32df07ca860887ea28b4a5c5e588042588563e3c7a6eab271068b2
Timestamp: 1706537520 Timestamp [UCT]: 2024-01-29 14:12:00 Age [y:d:h:m:s]: 01:009:06:29:24
Block: 945922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267688 RingCT/type: yes/0
Extra: 01d2a2252dda32df07ca860887ea28b4a5c5e588042588563e3c7a6eab271068b202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f34fdd33a0e2fe5a92d3416ba2f96140e4d9e7bf3936d3515c49d5e9524f113c 0.600000000000 1404248 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": 945932, "vin": [ { "gen": { "height": 945922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f34fdd33a0e2fe5a92d3416ba2f96140e4d9e7bf3936d3515c49d5e9524f113c" } } ], "extra": [ 1, 210, 162, 37, 45, 218, 50, 223, 7, 202, 134, 8, 135, 234, 40, 180, 165, 197, 229, 136, 4, 37, 136, 86, 62, 60, 122, 110, 171, 39, 16, 104, 178, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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