Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9d2b5040968cf361f8475b514d15b62f60fff90de43c6939a4e4ee4f65a5861

Tx prefix hash: 799e47ee5712f842e67a592d3eb386eacd9cb1d6433b394f8a8b83e701e0ecc5
Tx public key: f8785ac31472db7c7428353569b78ab2a734541c6fca04f6b97bd5f5c16a0433
Timestamp: 1709299300 Timestamp [UCT]: 2024-03-01 13:21:40 Age [y:d:h:m:s]: 01:055:15:16:29
Block: 968849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300774 RingCT/type: yes/0
Extra: 01f8785ac31472db7c7428353569b78ab2a734541c6fca04f6b97bd5f5c16a04330211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 508d5cdcd7e053e76cf0d757f5c0de5b11ee975e4db2b2d1f50f3e94cee67fcd 0.600000000000 1428672 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": 968859, "vin": [ { "gen": { "height": 968849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "508d5cdcd7e053e76cf0d757f5c0de5b11ee975e4db2b2d1f50f3e94cee67fcd" } } ], "extra": [ 1, 248, 120, 90, 195, 20, 114, 219, 124, 116, 40, 53, 53, 105, 183, 138, 178, 167, 52, 84, 28, 111, 202, 4, 246, 185, 123, 213, 245, 193, 106, 4, 51, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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