Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a653d142f31cd735144d65cc7d30d34017e7c4ed4831f59211c0137931d0478

Tx prefix hash: b336ef1b7f9a8e7968e18633b2b5a913bbc1f1b7c44fe462283874fc479eb462
Tx public key: 6e4864d0cb48922033bf1aa1f76974ae00787e16ba8d036ee91264ec1cb38a36
Timestamp: 1719698666 Timestamp [UCT]: 2024-06-29 22:04:26 Age [y:d:h:m:s]: 01:138:03:11:39
Block: 1055046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357279 RingCT/type: yes/0
Extra: 016e4864d0cb48922033bf1aa1f76974ae00787e16ba8d036ee91264ec1cb38a3602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a8ff84d32d25b0dba3af8f041d4caf1e02f8fe31f2fcee3a97af0e062d7d264 0.600000000000 1525439 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": 1055056, "vin": [ { "gen": { "height": 1055046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a8ff84d32d25b0dba3af8f041d4caf1e02f8fe31f2fcee3a97af0e062d7d264" } } ], "extra": [ 1, 110, 72, 100, 208, 203, 72, 146, 32, 51, 191, 26, 161, 247, 105, 116, 174, 0, 120, 126, 22, 186, 141, 3, 110, 233, 18, 100, 236, 28, 179, 138, 54, 2, 17, 0, 0, 0, 1, 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