Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf39a63e149706da7a7c27f65e05607d975b2dd77558f58b05c197cf92c0ba07

Tx prefix hash: 874c1ccdd7b0aa9443614342585f804f90fd3df0d6ecf0f0c023130d18e20ba9
Tx public key: b30e89ca1a118b632a418393f50f26f490b43c78d7057bb52ca916d07b4823a8
Timestamp: 1732410594 Timestamp [UCT]: 2024-11-24 01:09:54 Age [y:d:h:m:s]: 00:135:00:38:36
Block: 1160348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96302 RingCT/type: yes/0
Extra: 01b30e89ca1a118b632a418393f50f26f490b43c78d7057bb52ca916d07b4823a8021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 852e7421df636e1371e0e3bf0c0e32253d6be9093f156846e3039996892ee73d 0.600000000000 1645993 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": 1160358, "vin": [ { "gen": { "height": 1160348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "852e7421df636e1371e0e3bf0c0e32253d6be9093f156846e3039996892ee73d" } } ], "extra": [ 1, 179, 14, 137, 202, 26, 17, 139, 99, 42, 65, 131, 147, 245, 15, 38, 244, 144, 180, 60, 120, 215, 5, 123, 181, 44, 169, 22, 208, 123, 72, 35, 168, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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