Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbcfb240df2a7cc8b51e8c0a70bf75138f113aeff7415f0348a373549a7ac30e

Tx prefix hash: 1c7cce2156f1159568c86dc882cde10da0fc0796d19352483dcbd5ed6c250831
Tx public key: ae8c8d3fa94104095e3e3e5e52d47e3e5e7767926d075ead292859626ad89fad
Timestamp: 1716009505 Timestamp [UCT]: 2024-05-18 05:18:25 Age [y:d:h:m:s]: 00:322:10:47:21
Block: 1024471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230473 RingCT/type: yes/0
Extra: 01ae8c8d3fa94104095e3e3e5e52d47e3e5e7767926d075ead292859626ad89fad02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c316d51019579c41fee8f0c387fa849b858d09cce63a9fac61f52d5361b1db4a 0.600000000000 1490248 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": 1024481, "vin": [ { "gen": { "height": 1024471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c316d51019579c41fee8f0c387fa849b858d09cce63a9fac61f52d5361b1db4a" } } ], "extra": [ 1, 174, 140, 141, 63, 169, 65, 4, 9, 94, 62, 62, 94, 82, 212, 126, 62, 94, 119, 103, 146, 109, 7, 94, 173, 41, 40, 89, 98, 106, 216, 159, 173, 2, 17, 0, 0, 0, 7, 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