Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84b0cad8b96da59e2ea0247a8ef5c9064e8d733e146aee11baa223c724973753

Tx prefix hash: 4de7e19e1bdaa7291fc6d916e98e7d10a16cee16012a796ec5738f6bd2ae4d1f
Tx public key: 413be24199b5c428f23dd9eb4f7ae8161d4684a1944394ac7a105aa55249ff46
Timestamp: 1708647346 Timestamp [UCT]: 2024-02-23 00:15:46 Age [y:d:h:m:s]: 01:053:20:29:13
Block: 963432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299519 RingCT/type: yes/0
Extra: 01413be24199b5c428f23dd9eb4f7ae8161d4684a1944394ac7a105aa55249ff4602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37b6bb525627cf6c11a8ea91a18a8e7417e7b927f085cc5f67d49f31394af61e 0.600000000000 1423143 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": 963442, "vin": [ { "gen": { "height": 963432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37b6bb525627cf6c11a8ea91a18a8e7417e7b927f085cc5f67d49f31394af61e" } } ], "extra": [ 1, 65, 59, 226, 65, 153, 181, 196, 40, 242, 61, 217, 235, 79, 122, 232, 22, 29, 70, 132, 161, 148, 67, 148, 172, 122, 16, 90, 165, 82, 73, 255, 70, 2, 17, 0, 0, 0, 1, 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