Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23e108bcdfa06c4e44197f59e6dcd01bc0f4d8b3502bb8fab4fd1301c189c0c3

Tx prefix hash: 1463e2abf6844943b9a64aea18c1da8969439658e4a578aa282905c4b70819c5
Tx public key: abe50e0c7c5f543e0db4e21058c7556a23d1dc48a98ecd3504b914595fd3a88f
Timestamp: 1724250658 Timestamp [UCT]: 2024-08-21 14:30:58 Age [y:d:h:m:s]: 00:274:19:20:13
Block: 1092810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196296 RingCT/type: yes/0
Extra: 01abe50e0c7c5f543e0db4e21058c7556a23d1dc48a98ecd3504b914595fd3a88f02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d650b3a79eb78bc8c6457089e96490f5bfba8ad0324e09075c2eb4ed6985ab15 0.600000000000 1567631 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": 1092820, "vin": [ { "gen": { "height": 1092810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d650b3a79eb78bc8c6457089e96490f5bfba8ad0324e09075c2eb4ed6985ab15" } } ], "extra": [ 1, 171, 229, 14, 12, 124, 95, 84, 62, 13, 180, 226, 16, 88, 199, 85, 106, 35, 209, 220, 72, 169, 142, 205, 53, 4, 185, 20, 89, 95, 211, 168, 143, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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