Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4661b921d6a4f24f53945e54b62c1096adb54dfb69338beb0f061f0c6863ca3

Tx prefix hash: 1e54968908804336c6ed953320dd658ba1b967f9659d7a17a493d289140078a8
Tx public key: 3a035929f5b38bd3a0f234890eb2d320be25f102f1a09db7a83584977a0b5afb
Timestamp: 1674384079 Timestamp [UCT]: 2023-01-22 10:41:19 Age [y:d:h:m:s]: 01:355:21:35:00
Block: 680250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515360 RingCT/type: yes/0
Extra: 013a035929f5b38bd3a0f234890eb2d320be25f102f1a09db7a83584977a0b5afb0211000000035029cbac000000000000000000

1 output(s) for total of 3.420182709000 dcy

stealth address amount amount idx
00: f6f97adf89cfd8362bfa25fbd0d6cc8a937c325f7ca941bec8bf9b4f7540d308 3.420182709000 1122279 of 0

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": 680260, "vin": [ { "gen": { "height": 680250 } } ], "vout": [ { "amount": 3420182709, "target": { "key": "f6f97adf89cfd8362bfa25fbd0d6cc8a937c325f7ca941bec8bf9b4f7540d308" } } ], "extra": [ 1, 58, 3, 89, 41, 245, 179, 139, 211, 160, 242, 52, 137, 14, 178, 211, 32, 190, 37, 241, 2, 241, 160, 157, 183, 168, 53, 132, 151, 122, 11, 90, 251, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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