Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 010710cab709c475e18f3784540c7a99f43354fcbdb7a5cb4bfb9b0f788d080f

Tx prefix hash: 16ec342e2c521fcb793aa70ba6db39074c331b9ef4117ca390647f4c01f7fb36
Tx public key: ac34fe7dadf5032cb89b084e7658d3b2855dbdd1499727dccc3c858eb0e4c566
Timestamp: 1711848413 Timestamp [UCT]: 2024-03-31 01:26:53 Age [y:d:h:m:s]: 01:082:16:07:39
Block: 989990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319908 RingCT/type: yes/0
Extra: 01ac34fe7dadf5032cb89b084e7658d3b2855dbdd1499727dccc3c858eb0e4c56602110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c08968aae5e005b5db2bf6358097ae56a8ce4d55abba3c11b708c75c90d38a40 0.600000000000 1450308 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": 990000, "vin": [ { "gen": { "height": 989990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c08968aae5e005b5db2bf6358097ae56a8ce4d55abba3c11b708c75c90d38a40" } } ], "extra": [ 1, 172, 52, 254, 125, 173, 245, 3, 44, 184, 155, 8, 78, 118, 88, 211, 178, 133, 93, 189, 209, 73, 151, 39, 220, 204, 60, 133, 142, 176, 228, 197, 102, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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