Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c5e2bf2a5d772d830b0b6db22ed2494aae318d36b3188db0cdbe5e8f7848e7f

Tx prefix hash: 95620156abefa53143e9df8f74c0ed036c31b26ddb45f7846e5abe104b174efb
Tx public key: e34f430f3944e1eb3f2bd1995a1097966608ff9d3b8659237b72c07d614deff7
Timestamp: 1724456082 Timestamp [UCT]: 2024-08-23 23:34:42 Age [y:d:h:m:s]: 00:236:20:52:04
Block: 1094507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169143 RingCT/type: yes/0
Extra: 01e34f430f3944e1eb3f2bd1995a1097966608ff9d3b8659237b72c07d614deff7021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e51e5a467acbcbf3fc925eeac212ce3f0ea2a568e5b84a35cd7a790a4c93c82 0.600000000000 1569624 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": 1094517, "vin": [ { "gen": { "height": 1094507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e51e5a467acbcbf3fc925eeac212ce3f0ea2a568e5b84a35cd7a790a4c93c82" } } ], "extra": [ 1, 227, 79, 67, 15, 57, 68, 225, 235, 63, 43, 209, 153, 90, 16, 151, 150, 102, 8, 255, 157, 59, 134, 89, 35, 123, 114, 192, 125, 97, 77, 239, 247, 2, 17, 0, 0, 0, 4, 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