Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fce370e7cc1920aedfdf0eb58bd955c78f35415554d18bc87940ab03c82edbe3

Tx prefix hash: 998d520227d94692b98d42a4a7f8c638748f93ce8c25d752e1ec6d0b8847c89c
Tx public key: 1d324e565c5daabd2b82c53aae2607443c595c7aea85f979c63e843bf88c3f75
Timestamp: 1699854287 Timestamp [UCT]: 2023-11-13 05:44:47 Age [y:d:h:m:s]: 01:079:16:53:00
Block: 890544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318107 RingCT/type: yes/0
Extra: 011d324e565c5daabd2b82c53aae2607443c595c7aea85f979c63e843bf88c3f75021100000004faf35c9c000000000000000000

1 output(s) for total of 0.687476794000 dcy

stealth address amount amount idx
00: 821243d5183016c11627db5e8fb27e74add92edcbcf79b64ce77a5c0c7b0f3c1 0.687476794000 1346567 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": 890554, "vin": [ { "gen": { "height": 890544 } } ], "vout": [ { "amount": 687476794, "target": { "key": "821243d5183016c11627db5e8fb27e74add92edcbcf79b64ce77a5c0c7b0f3c1" } } ], "extra": [ 1, 29, 50, 78, 86, 92, 93, 170, 189, 43, 130, 197, 58, 174, 38, 7, 68, 60, 89, 92, 122, 234, 133, 249, 121, 198, 62, 132, 59, 248, 140, 63, 117, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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