Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3af0b07592018c0be489ba6d5736925d132a307078c0dee24939c0382b0a709

Tx prefix hash: 59084fdf528a828f26f92649e163cd0ad68f62787ee8f589e7d2e0297b0d96d3
Tx public key: 44ce12bff535cee4e08f5d78e2130c1b15fadc5c628e36ed2ed16f4b6b383108
Timestamp: 1720241748 Timestamp [UCT]: 2024-07-06 04:55:48 Age [y:d:h:m:s]: 00:319:21:25:19
Block: 1059557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228620 RingCT/type: yes/0
Extra: 0144ce12bff535cee4e08f5d78e2130c1b15fadc5c628e36ed2ed16f4b6b3831080211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96ac2aca1bc68b6693d13529164dc97aa7a797cfec02ddc1ed69c3982f35da45 0.600000000000 1530026 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": 1059567, "vin": [ { "gen": { "height": 1059557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96ac2aca1bc68b6693d13529164dc97aa7a797cfec02ddc1ed69c3982f35da45" } } ], "extra": [ 1, 68, 206, 18, 191, 245, 53, 206, 228, 224, 143, 93, 120, 226, 19, 12, 27, 21, 250, 220, 92, 98, 142, 54, 237, 46, 209, 111, 75, 107, 56, 49, 8, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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