Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2331872af3c6ca09734b0af477c86d5ad909a8f150c1237cc8cf3048a5c92b7

Tx prefix hash: 47f327d15b8e48fd42e08b8cbba0e1156e4e9b389e7b9e836b69a742d04233a2
Tx public key: 32a85b4c2752bf65c9d981b14b66bb2e41bc325170e447223d2ce131fc69232a
Timestamp: 1704386422 Timestamp [UCT]: 2024-01-04 16:40:22 Age [y:d:h:m:s]: 01:309:07:59:16
Block: 928118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479889 RingCT/type: yes/0
Extra: 0132a85b4c2752bf65c9d981b14b66bb2e41bc325170e447223d2ce131fc69232a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6c559095fea808a07a4b911939c6eee3f7f90e8b5066e4550cfe090958d67a5 0.600000000000 1385974 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": 928128, "vin": [ { "gen": { "height": 928118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6c559095fea808a07a4b911939c6eee3f7f90e8b5066e4550cfe090958d67a5" } } ], "extra": [ 1, 50, 168, 91, 76, 39, 82, 191, 101, 201, 217, 129, 177, 75, 102, 187, 46, 65, 188, 50, 81, 112, 228, 71, 34, 61, 44, 225, 49, 252, 105, 35, 42, 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