Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de194aee5269b1f4e77f11b935a318c48f8335f2e6e8efb4cf6f48e9b710f4a1

Tx prefix hash: 2f043662732b19bba97a86b0c4cc39b2917ef2c0a0f36a5fa5644294f641af34
Tx public key: 0f66011a1a04502c3fc4e319ad192fc2c115b6e7e2aaa90e03717fcfb484da27
Timestamp: 1700941980 Timestamp [UCT]: 2023-11-25 19:53:00 Age [y:d:h:m:s]: 01:133:06:25:21
Block: 899554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356391 RingCT/type: yes/0
Extra: 010f66011a1a04502c3fc4e319ad192fc2c115b6e7e2aaa90e03717fcfb484da27021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.641806571000 dcy

stealth address amount amount idx
00: c89576981a8a4cff63b8e6980091a49a00a65a60996cd2d834e850c7e9cc3aec 0.641806571000 1356013 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": 899564, "vin": [ { "gen": { "height": 899554 } } ], "vout": [ { "amount": 641806571, "target": { "key": "c89576981a8a4cff63b8e6980091a49a00a65a60996cd2d834e850c7e9cc3aec" } } ], "extra": [ 1, 15, 102, 1, 26, 26, 4, 80, 44, 63, 196, 227, 25, 173, 25, 47, 194, 193, 21, 182, 231, 226, 170, 169, 14, 3, 113, 127, 207, 180, 132, 218, 39, 2, 17, 0, 0, 0, 8, 230, 210, 127, 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